Identity data based on aggregating input data

ABSTRACT

A computing device, a system, and a method are provided to receive a number of inputs associated with one or more sensors of the computing device. One or more processors are configured to determine input data based on the number of inputs and authenticate a user account based on the input data. A communication interface is enabled to communicate with one or more devices based on the authentication. Further, the system may aggregate the input data based on the number of inputs. The system may determine identity data of the user account based on the aggregation. The system may transmit an indication of the identity data to the computing device.

TECHNICAL FIELD

This disclosure generally relates to computing devices, and moreparticularly, determining identity data based on an aggregation of inputdata from the computing devices and the user.

BACKGROUND

Various computing devices such as personal computers, laptop computers,tablet computers, smart phones, and numerous other devices areincreasingly more prevalent in the technological landscape. With theadvent of these devices conforming to numerous aspects of modernlifestyles, the manner in which these devices provide data is becomingmore intelligent, efficient, and intuitive. As such, various trendstowards miniaturization of biometric sensors, computing hardware,peripherals, processors, among other forms of technologies, have helpedpave the way for technology referred to mobile computing devices andwearable computing devices.

Many computing devices are designed to be carried or worn from onelocale to another with minimal effort. Yet, such designs have opened upa myriad of possible issues. For example, the effortless transferabilityof such devices has created numerous opportunities for theft and takingthese devices away from their rightful owners. As a result, fraudulentactivities through such computing devices are also becoming moreprevalent as unauthorized users perform actions using these deviceswithout rightful consent.

Even further, various forms of security technologies have been provenineffective. For example, biometric security measures generally requiresome active step taken by the owner, such as pressing a finger on afingerprint sensor for locking or unlocking the device. Yet, suchmeasures have inconsistencies and varying levels of success becauseproviding fingerprint data simply to operate the device may beinconvenient and inefficient as well. Further, these biometric dataitself is also susceptible to theft such that these security measuresmay be wholly circumvented by interceptors who may copy and use thebiometric data to gain unauthorized accesses.

Thus, there is much need for improvement in security technology relatedto computing devices.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A and 1B illustrate an exemplary computing device, according toan embodiment;

FIG. 2 illustrates an exemplary computing device, according to anembodiment;

FIG. 3 illustrates a block diagram of an example system, according to anembodiment;

FIG. 4A illustrates an exemplary server device configured to support aset of trays, according to an embodiment;

FIG. 4B illustrates an exemplary tray configured to support one or morecomponents, according to an embodiment;

FIG. 5 is an exemplary system, according to an embodiment;

FIG. 6 is a flowchart of an exemplary method, according to anembodiment;

FIG. 7 is an exemplary system, according to an embodiment; and

FIG. 8 illustrates an exemplary wearable computing device, according toan embodiment.

Embodiments of the present disclosure and their advantages may beunderstood by referring to the detailed description that follows. Itshould be appreciated that like reference numerals are used to identifyelements illustrated in one or more of the figures, where the figuresillustrate various examples for purposes of examples and explanationrelated to the embodiments of the present disclosure and not forpurposes of limitation.

DETAILED DESCRIPTION

A computing device may include one or more sensors configured tointerface with humans and receive numerous inputs accordingly. One typeof input such as, for example, a drop of sweat or saliva may be used toidentify a particular user. Further, in addition to active inputs suchas fingerprint inputs and voice command inputs, passive inputs may alsobe received such as movement inputs based on the way a particular usermoves, talks, eats, walks, gestures via hands or fingers, and/or changesdirection, among other natural movements that may be used to recognizethe user. By identifying various forms of data based on a number of suchinputs, the computing device may authenticate the user's account,enabling the device to authorize activities under the account.

Even further, by tracking inputs as the user goes about the day, theauthentication of the account may be continuously verified. For example,a second attachable computing device may be clipped on to the user'sclothing or otherwise carried by the user to receive a second set ofinputs, possibly to confirm the passive inputs received by the computingdevice described above so as to continually verify the authentication ofthe user account. Based on this continual verification, the computingdevice may be enabled to securely communicate with other devices (e.g.,merchant devices) and applications (e.g., online shopping websites). Forinstance, the computing device may communicate without having totransfer any authentication data to the other devices and/orapplications so as to indicate the user account is authenticated. Thus,the user may be able to seamlessly authorize activities with merchantdevices and applications without swiping credit cards, showingidentification, logging in to applications, and/or taking otherconventional steps to show the user account is properly authenticated.

Moreover, by accessing the several inputs in the manner above, variousportions of the input data may be aggregated from the computing deviceand/or the attachable computing device. In the aggregation process, asystem may compile such portions to determine an identity of the useraccount and provide recommendations to the user. For example, the systemmay determine various identities of a user account (e.g., the usershopping at a mall location) and thereby recommend items based onshopping patterns at the mall location, possibly identified from theinput data such as movement data indicating the way the user stops atgiven stores to look at particular items. In practice, the system may,for example, determine an identity or activity of the user shopping forpants and trying on different pairs of pants based on movement data ofthe user. Thus, the system may recommend pants offered at specificstores in the mall location, possibly based on one or more sizes of theuser determined from the input data and/or historical user data based onprior shopping experiences.

FIGS. 1A and 1B provide an exemplary a computing device 100, accordingto an embodiment. The computing device 100 may take the form of asmartphone. Further, as shown, the computing device 100 may take theform of a wearable computing device. The computing device 100 mayinclude a head-mountable display and an arm or wrist-mountable display.As shown in FIG. 1A, the computing device 100 may be wearable as ahead-mountable device (HMD). The computing device 100 may include lenses102 and 104. The computing device 100 may also include a side component106, a side component 108, and a middle component 110. For example, thecomputing device 100 may be mountable on a user's head such that theside component 106 rests on one ear of the user and the side component108 rests on the other ear of the user. Further, the middle component110 may rest on the nose of the user. In some instances, the lenses 102and 104 may be positioned in front of the user's eyes. Further, thelenses 102 and 104 may include displays 112 and 114, respectively. Insome instances, the displays 112 and 114 may be transparent, partiallysee-through, and/or configured to provide an augmented reality. Further,the displays 112 and/or 114 may display data and receive proximityinputs (e.g., capacitive sensing inputs) such that the user canmanipulate graphics provided by the displays 112 and/or 114. The lenses102 and/or 104 may also include scanners such as laser scannersconfigured to scan the eyes of the user to retrieve biometric data fromthe user's eyes, retinas, and/or irises, possibly for authenticating theuser's account.

As shown in FIG. 1B, the computing device 100 may also take the form ofan arm/wrist-mountable device or a smart watch. Yet, the computingdevice 100 may take the form of a bracelet, an anklet, and/or anecklace, among other forms of jewelry. As shown, the band 128 may beadjustable to fit on an arm and/or wrist 124 of a user. As shown, thecase 126 may be positioned on the top of the wrist 124 to operate as theface of a wrist watch. The band 128 may be configured to detect one ormore patterns of pulses from the wrist 124 of the user, possibly forauthenticating the user's account.

The computing device 100 may include one or more sensors 116 and/or 118configured to receive a number of inputs associated with the user. Theone or more sensors 116 and/or 118 may include accelerometers,gyroscopes, compasses, barometers, capacitive sensors, haptic sensors,temperature sensors, ambient light sensors, sound sensors, imagesensors, biometric sensors, moisture sensors, electrodes, and/orchemical sampling sensors, among other types of sensors to receiveinputs from human matter. For example, based on the way the computingdevice 100 is worn as a head-mountable device or an arm/wrist-mountabledevice, the sensors 116 and/or 118 may be configured to receive inputsdirectly and/or indirectly from skin, sweat, saliva, blood, nails,and/or hair, among other inputs related to the user.

Further, the computing device 100 may include one or more processingcomponents 120 configured to determine input data based on the number ofinputs. For example, input data may include Deoxyribonucleic acid (DNA)data, salivary data, sweat data, pulse data, hair data, nail data, blooddata, and/or a combination of such data, among other forms of datarelated to the user.

Yet further, the one or more processor components 120 may authenticate auser account based on the input data. The one or more processorcomponents 120 may utilize built-in logic to compare various forms ofthe determined input data with data associated with the user account.For example, the DNA data from the input data may be compared with DNAassociated with the user account. The one or more processor components120 may determine a match or a partial match to authorize a user tooperate the computing device 100. Thus, the one or more processorcomponents 120 may authenticate the user account based on such matchesdetermined.

In addition, the computing device 100 may include a communicationinterface 122 that may be enabled to communicate with one or more otherdevices based on the authentication of the user account. For example,the communication interface 122 may be disabled unless and/or until theone or more processors 120 authenticates the user account. Thus, thecommunication interface 122 may be disabled such that it cannotcommunicate with any other devices and/or applications, thereby securingdata within the computing device 100. Yet, based on the authenticationof the user account, the communication interface 122 may be enabled tocommunicate with the other devices and/or applications to authorizeactivities of the user account. For example, based on the communicationwith the other devices, the communication interface may access secondinput data based on a second plurality of inputs associated with theuser.

The one or more sensors 116 and/or 118 may be further configured todetermine whether the computing device 100 is separated from the user,such as the arm or wrist 124. For example, the one or more sensors 116and/or 118 may include a capacitance sensor that measures thecapacitance and changes in the capacitance based on the computing device100 being separated from the user. Another example may involve a pulsesensor periodically measuring the pulse of the wrist 100. The one ormore processing components 120 may be further configured to modify theauthentication of the user account based on the determination of theseparation and/or the measurements of the pulse. For instance, a thiefmay snatch the computing device 100 off of the wrist 124 of the rightfulowner, where the one or more sensors 116 and/or 118 may detect thedevice is separated from the owner. Furthermore, the one or more sensors116 and/or 118 may no longer detect the user's pulse patterns, possiblyunique to the user. Thus, the one or more processing components 120 maydisable or withdraw the authentication, possibly powering down thecomputing device 100 and/or disabling the communication interface 122,as described above.

The one or more processors components 120 may be further configured todetermine passive input data from the input data and verify theauthentication of the user account based on the passive input data. Forexample, the one or more processor components 120 may determine variousforms of movement data associated with the user account to continuallyverify the authentication. In some instances, when the computing device100 is worn on the user's wrist 124, the processor components 120 maydetermine movement data indicating how the computing device 100 moveswith the wrist 124 as the user naturally walks. The movement data mayindicate certain patterns based on the user's strides to verify theauthentication of the user account. Further, when the computing device100 is worn on the user's head, the one or more processor components 120may determine movement data indicating how the computing device 100moves on the user's head as the user eats breakfast and/or talks duringbreakfast to verify the authentication of the account.

In some instances, the passive input data may include movement dataand/or size data associated with the user. Further, the one or moreprocessing components 120 may be configured to verify the authenticationof the user account based on the movement data, the size data, and/or acombination of such data. In one example, the one or more processingcomponents 120 may determine a combination of the movement data and sizedata based on the computing device 100 being worn on the user's wrist124 during one or more steady states, where the size data may be basedon the circumference of the user's wrist 124 measurable by the band 128of computing device 100. Based on the combination of the movement dataand size data matching those associated with the user account, theauthentication of the user account may be verified.

In some instances, the one or more other devices may include ancomputing device 200 configured to receive a second number of inputsassociated with the user via the one or more sensors 202. FIG. 2provides an exemplary a computing device 200, according to anembodiment. The computing device 200 may take the form of a smartphone.Further, as shown, the computing device 200 may take the form of anattachable computing device. The one or more sensors 202 may, forexample, take the form of the one or more sensors 116 and/or 118 of thecomputing device 100. The communication interface 122 of the computingdevice 100 may be configured to access the second number of inputsreceived by the attachable computing device 200. Further, the one ormore processing components 120 of the computing device 100 may befurther configured to determine second input data based on at least thesecond plurality of inputs. As such, the one or more processingcomponents 120 may verify the authentication of the user account basedon at least the second input data. Further, the computing device 100 mayutilize the second input data to verify (e.g., check the accuracy orprecision) of the input data from the one or more sensors 116 and/or118, possibly in the presence of noise and/or other interferences. Yetfurther, the computing device 100 may utilize the second input data whenthe one or more sensors 116 and/or 118 are not receiving input data,possibly due to damage and/or a slight or temporary separation of thecomputing device 100 from the user.

As shown, the computing device 200 may clip on to the computing device100 using a clip 204. Further, the computing device 200 may clip on atie, a belt buckle, and/or other piece of clothing, among othermaterials to be located proximate to the computing device 100. Yetfurther, the computing device 200 may take the form of a piece ofjewelry such as an earring, a ring, a bracelet, and/or a watch that maymake contact with the user's skin to receive biometric data. In someinstances, the communication interface 122 of the computing device 100may connect or link with the attachable computing device 200, possiblythrough a short-range wireless communication protocol such as BLUETOOTHor BLE (BLUETOOTH LOW ENERGY). Based on the connection and/or link, thecomputing device 100 may indicate or trigger various identities such asa shopping identity such that the computing device 100 may communicatewith merchant devices and/or applications to authorize one or moreactivities under the user account.

The one or more processing components 120 may be further configured todetermine identity data of the user account based on an aggregation ofthe first input data from the computing device 100 and second input datafrom the attachable computing device 200. For example, various portionsof the input data described above may be aggregated to determine theidentity data. As such, the identity data may indicate one or moreactivities of the user account, such as shopping for a gift or clothing,shopping for groceries, running an errand, using an automated tellermachine (ATM), bargain hunting, and/or eating/drinking food/beverages,among other activities of the user account. Further, the communicationinterface 124 may be configured to communicate with a merchant device ofthe one or more other devices based on the identity data. In someinstances, the communication interface 122 may be configured to accessone or more applications and secure the identity data and the first andsecond input data from the one or more applications such that the one ormore applications are unable to access the identity data and the inputdata.

In some embodiments, a user account, possibly also referred to as anaccount, may be a compilation of data associated with a user and/or theuser's interests. As such, some examples may include accounts to aninternational digital wallet, possibly based on an e-commerce business,such as PAYPAL®, of San Francisco, Calif., USA and/or accounts to anonline service for tickets to events, such as STUBHUB®, of SanFrancisco, Calif., USA. Further, some examples of accounts may includee-mail accounts, social networking accounts, financial accounts,e-commerce accounts, smartphone accounts, wearable computing deviceaccounts, and/or accounts with service providers, among otherpossibilities. For example, an account for a particular user may includedata related to the user, data related to the user's interest, and/ordata representing the user. In some embodiments, a user may have asingle account to an international digital wallet representing the userfor multiple other accounts described above such as a social networkingaccount, an e-mail account, and/or a financial account, as well aswebsites, applications, and/or other services. For example, a user couldopt to use their digital wallet account as a multi-purpose account. Forexample, the user may use the digital wallet account to search foravailable items at store locations.

The user account may be displayed on a computing device, such as thosedescribed above in relation to FIGS. 1A and 1B. As such, the useraccount may be displayed on a smartphone, a laptop computer, and/or atablet computer, among other devices that may be used to access theaccount. The user may operate the computing device and their account maybe managed on the computing device. For example, the computing devicemay be used to receive account data, send search requests, and/or storedata associated with the account such that details regarding the accountmay be viewed on the computing device. Further, login information may beprovided to authenticate the account and payment information may beprovided to secure and/or purchase items under the account.

In some embodiments, a user account may indicate or recommend variousitems that the user may be interested in. For example, the user accountmay identify or recommend types of clothing or brands, categories offood or beverages, and/or genres of movies or films, among other itemsthat the user may be interested in. Further, the user account mayidentify or recommend sporting teams, music groups, and/or comediansthat the user may be interested in. For example, the computing devicesdescribed above may gather data regarding the user and compile the datato the user's account. In particular, the computing device may trackprevious purchases at given store locations and update the user accountaccordingly, possibly to predict or recommend future purchases,incentives, or items that the user may be interested in. Further, thecomputing device may track user's preferences of available items at thegiven store locations and update the user account accordingly withpossible recommended items. As such, the computing device may providesuch recommendations when the user is proximate to the store locations.

In some embodiments, an account may be created by one or more users.Further, the account may be created by services, applications, and/orother websites, among other possibilities. As such, various users mayhave access to a particular account. For example, the user may be acorporation with access to a corporate account, possibly for itsemployees, staff, worker personnel, and/or contractors, among otherindividuals. Yet further, a user may be a computing device, a computingsystem, a robotic system, and/or another form of technology capable ofsending and receiving data corresponding to the account. A user mayprovide a login, a password, a code, authentication data, biometricdata, and/or other types of data to access the account.

FIG. 3 is a block diagram of an example system 300, according to anembodiment. As shown, the system 300 includes multiple computingdevices, such as a server device 302, a client device 304 that may takethe form of the computing device 100, and a client device 306 that maytake the form of the computing device 200, among other possiblecomputing devices. The server device 302 may be configured to support,manage, and/or aggregate input data from client devices 304 and/or 306.The system 300 may operate with more or less computing devices thanthose shown in FIG. 3, where each device may be configured tocommunicate over a communication network 308. As shown, the serverdevice 302, the client device 304, and the client device 306 are eachconfigured to communicate over the communication network 308.

The server device 302 may be configured to perform various operations inaccordance with this disclosure and the accompanying figures. Forexample, the server device 302 may access a number of the inputsreceived by the client device 304 and/or the client device 306. Inparticular, the server device 302 may aggregate input data associatedwith the number of inputs received by the client devices 304 and/or 306.For example, the server device 302 may aggregate various forms of inputdata such as, for example, the input data described above in relation toFIGS. 1-2. Further, the server device 302 may determine identity data ofthe user account based on the aggregation of the input data. Yet,further, the server device 302 may send various indications, e.g.,recommendations, to the client device 304 and/or 306 accordingly.

In some embodiments, the server device 302 may take a variety of formsand may include a multiple components, including for example, acommunication interface 312, a transceiver 314, one or more processingcomponents 316, a data storage 318, and an engine 320 any of which maybe communicatively linked to the other components via a system bus,network, or other connection mechanism 324.

The communication interface 312 may take a variety of forms and may beconfigured to allow the server device 302 to communicate with one ormore devices 304 and/or 306 according to a number of protocols. Forexample, the communication interface 312 may include the transceiver 314configured to allow the server device 302 to communicate with the clientdevices 304 and/or 306 via communication network 308. In one example,the communication interface 312 and/or the transceiver 314 may take theform of a wired interface, such as an Ethernet interface. As anotherexample, the communication interface 312 and/or the transceiver 314 maytake the form of a wireless interface, such as a cellular interface, aWI-FI interface, another short-range, point-to-multipoint voice and/ordata transfer communication interface, such as BLUETOOTH or BLE(BLUETOOTH LOW ENERGY).

The one or more processing components 316 may take the form of a generalpurpose processor (e.g., a microprocessor) and/or a special purposeprocessor such as a digital signal processor (DSP), an applicationspecific integrated circuit (ASIC), a programmable system on chip(PSOC), field-programmable gate array (FPGA), and/or another processingcomponent configured to process input data, passive input data, locationdata, identity data, account data, and/or other types of data. Forexample, the data packets 326 and/or 328 may be accessed from the clientdevices 304 and 306, respectively, over the communication network 308.Further, the data packets 326 and 328 may include IP addresses of theclient device 304 and 306, respectively. One or more of the processingcomponents 316 may access the data packets 326 and/or 328 associatedwith a user account accessible by the client device 304. Yet further,the data packets 326 and 328 may be accessible via protocols such asTransmission Control Protocol/Internet Protocol (TCP/IP). In variousembodiments, each of the packets 326 and 328 may include 1,000 to 1,500bytes, among other possible ranges.

The data storage 318 may include one or more of volatile, non-volatile,and/or removable storage components, such as magnetic, optical, or flashstorage, and may be integrated in whole or in part with the one or moreprocessing component. Further, the data storage 318 may include or takethe form of a non-transitory computer-readable storage medium, havingstored thereon machine- or computer-readable instructions (e.g.,compiled or non-compiled program logic and/or machine code) that, whenexecuted by the server device 302, cause the server device 302 toperform operations, such as those described in this disclosure andillustrated by the accompanying figures.

The database engine 320 may include numerous databases for storing,processing, and/or securing data of the server 302. For example, thedatabase engine 320 may include relational databases for onlinetransaction processing and/or online analytical processing. The databaseengine 320 may generate numerous search queries, search multipledatabases parallel, and produce search results simultaneously and/orconsecutively. As such, the database engine 320 may create multipletables, database objects, indices, and/or views to perform the onlinetransaction processing and/or analytical processing.

The client devices 304 and 306 may also be configured to perform avariety of operations such as those described in this disclosure andillustrated by the accompanying figures. For example, client devices 304and 306 may be configured to exchange data packets with the serverdevice 302, such as data packets 326 and 328 including input data,passive input data, location data, identity data, account data, and/orother types of data. Client devices 304 and 306 may take a variety offorms, including for example, a wearable computing device, a personalcomputer (PC), a smartphone, a laptop/tablet computer, a merchantdevice, a smart watch with appropriate computer hardware resources,and/or other types of computing devices capable of transmitting and/orreceiving data. Client devices 304 and 306 may include variouscomponents, including, for example, input/output (I/O) interfaces 330and 340, communication interfaces 332 and 342, processors 334 and 344,and data storages 336 and 346, respectively, all of which may becommunicatively linked with each other via a system bus, network, orother connection mechanisms 338 and 348, respectively.

The I/O interfaces 330 and 340 may be configured for facilitatinginteraction between client devices 304 and 306 and the user of clientdevices 304 and 306, possibly accessing their account via the clientdevices 304 and 306. In some instances, the I/O interfaces 330 and 340may include sensors such as those described above in relation to FIGS.1-2. The sensors may be configured to receive inputs from a user andpossibly provide outputs to the user. The I/O interfaces 330 and 340 mayalso include input hardware such as a touchscreen, a touch sensitivepanel, a microphone for receiving voice commands, a computer mouse, akeyboard, and/or other input hardware. In addition, I/O interfaces 330and 340 may include output hardware such as displays possibly withtouchscreen inputs, a sound speaker, other audio output mechanism, ahaptic feedback system, and/or other output hardware.

In some embodiments, communication interfaces 332 and 342 may take avariety of forms and may be configured to allow client devices 304 and306 to communicate with one or more devices according to any number ofprotocols. For instance, communication interfaces 332 and 342 may beconfigured to allow client devices 304 and 306, respectively, tocommunicate with the server device 302 via the communication network308. The processors 334 and 344 may include general purpose processorsand/or special purpose processors. The data storages 336 and 346 mayinclude one or more volatile, non-volatile, and/or removable storagecomponents, and may be integrated in whole or in part with processors334 and 344, respectively. Further, the data storages 336 and 346 maytake the form of non-transitory computer-readable storage mediums,having stored thereon machine- or computer-readable instructions that,when executed by processors 334 and 344, cause client devices 304 and306 to perform operations, respectively, such as those described in thisdisclosure and illustrated by the accompanying figures. Such machine- orcomputer-readable instructions may define or be part of a discretesoftware application, such a native app and/or web app, that may beexecuted upon user input.

In some embodiments, the communication network 308 may exchange dataamong the server device 302, the client device 304, the client device306, and/or other client devices. The communication network 308 may be apacket-switched network configured to provide digital networkingcommunications and/or exchange data of various forms, content, type,and/or structure. The communication network 308 may correspond to smallscale communication networks, such as a private and/or local areanetwork. The communication network 308 may also correspond to a largerscale network, such as a wide area network or the Internet, possiblyaccessible by the various devices of system 300. The communicationnetwork 308 may include network adapters, switches, routers, networknodes, and/or various buffers and queues to exchange data packets. Forexample, the communication network 308 may be configured to carry datapackets such as a first data packet 326 and a second data packet 328including input data, passive input data, location data, identity data,account data, and/or other types of data. The server device 302 mayexchange such packets 326 and/or 328 between the client device 304and/or the client device 306 over the communication network 308 usingvarious protocols such as Transmission Control Protocol/InternetProtocol (TCP/IP), among other possibilities.

It can be appreciated that the server device 302 and the client device304 and 306 illustrated in FIG. 3 may be deployed in other ways suchthat the operations performed by such devices may be combined orseparated for a given embodiment. Notably, the operations may beperformed by a greater number or a fewer number of devices and/or serverdevices.

FIG. 4A illustrates an exemplary server device 400 configured to supporta set of trays, according to an embodiment. Server device 400 may, forexample, take the form of the server device 302 described above.Further, the server device 400 may be configured to support, operate,run, and/or manage a user account service and various types of dataincluding input data, passive input data, location data, identity data,account data, and/or other types of data.

As shown, server device 400 may include a chassis 402 that may supporttrays 404 and 406, and possibly multiple other trays as well. Thechassis 402 may include slots 408 and 410 configured to hold trays 404and 406, respectively. For example, the tray 404 may be inserted intothe slot 408 and the tray 406 may be inserted into the slot 410. Yet,the slots 408 and 410 may be configured to hold the trays 404 and 406interchangeably such that the slot 408 may be configured to hold thetray 406 and the slot 410 may be configured to hold the tray 404.

The chassis 402 may be connected to a power supply 412 via connections414 and 416 to supply power to the slots 408 and 410, respectively. Thechassis 402 may also be connected to communication network 418 viaconnections 420 and 422 to provide network connectivity to the slots 408and 410, respectively. As such, trays 404 and 406 may be inserted intoslots 408 and 410, respectively, and power supply 412 may supply powerto trays 404 and 406 via connections 414 and 416, respectively.

The communication network 418 may, for example, take the form ofcommunication network 308 described above in relation to FIG. 3. In someembodiments, communication network 418 may provide a network port, anetwork hub, a network switch, or a network router that may be connectedto a telephone, Ethernet, or an optical communication link, among otherpossibilities.

FIG. 4B illustrates an exemplary tray 404 configured to support one ormore components, according to an embodiment. The tray 404 may, forexample, take the form of tray 404 described in relation to FIG. 4A. Asshown, the tray 404 may include a tray base 430 as the bottom surface ofthe tray 404 configured to support multiple components such one or morecomponents 432-440. The tray 404 may include a connector 426 that maylink to the connections 414 or 416 to supply power to the tray 404. Thetray 404 may also include a connector 428 that may link to theconnections 420 or 422 to provide network connectivity to the tray 404.The connectors 426 and 428 may be positioned on the tray 404 such thatupon inserting the tray 404 into the slot 408, the connectors 426 and428 couple directly with the connections 414 and 420, respectively.Further, upon inserting the tray 404 into the slot 410, the connectors426 and 428 may couple directly with connections 416 and 422,respectively.

The tray 404 may include components 432-440. In some instances, acommunication interface 432, a transceiver 434, one or more processingcomponents 436, a data storage 438, and a database engine 420 may, forexample, take the form of the communication interface 312, thetransceiver 314, the one or more processing components 316, the datastorage 318, and the data base engine 320, respectively. As such, theserver 400 and the tray 404 may be configured to provide power andnetwork connectivity to each of the components 432-440. In someembodiments, one or more of the components 432-440 may be configured tooperate via one or more circuits that include resistors, inductors,capacitors, voltage sources, current sources, switches, logic gates,registers, and/or a variety of other circuit elements. One or more ofthe circuit elements in a circuit may be configured to provide supportthe components 432-442 to perform the operations described herein. Assuch, in some embodiments, preconfigured and dedicated circuits may beimplemented to perform the operations of the components 432-440. In someembodiments, a system may execute instructions on a non-transitory,computer-readable medium to configure one or more circuits as requiredto perform the operations described herein and illustrated by theaccompanying figures.

Any two or more of the components 432-440 described above may becombined to take the form of one or more general purpose processors,microprocessors, and/or special purpose processors, among other types ofprocessors. For example, two or more of the communication interface 432,the transceiver 434, the one or more processing components 436, and thedata storage 442 may be combined with and/or within a processing device.Further, the combined processing device may take the form of one or morenetwork processors, DSPs, PSOCs, FPGAs, and/or ASICs, among other typesof processing devices and/or components. As such, the combinedprocessing device may be configured to carry out various operations ofthe components 432-440.

A system may include a non-transitory computer-readable medium, such asthose described in FIGS. 3-4. The medium may have stored thereonmachine- or computer-readable instructions that are executable by aserver device, such as the server devices 302 and/or 400. When theinstructions are executed, the server device may perform variousoperations. For example, the operations may include accessing, by acommunication interface of the server device, a number of inputsreceived by a computing device. In particular, the communicationinterface, such as the communication interfaces 312 and/or 412, mayaccess the number of inputs. Further, the communication interface mayaccess the number of inputs received by a computing device, such as thecomputing device 100 and/or the computing device 200, as describedabove.

The operations may also include aggregating, by one or more processingcomponents of the server device, input data associated with the numberof inputs. In some instances, the one or more processing components mayaggregate the input data from a number of client devices such as thecomputing device 100 and/or the attachable computing device 200. The oneor more processing components, such as the processing components 316and/or 436, may aggregate the input data in a database engine of theserver device, such as the database engines 320 and/or 440.

The operations may also include determining, by the one or moreprocessing components, identity data of a user account based on theaggregation of the input data, where the identity data indicates one ormore activities such as those described above associated with the useraccount. For example, the one or more processing components maydetermine the identity data of the user account from the input dataaggregated in the database engines 320 and/or 440. The one or moreprocessing components may organize, select, and/or modify the variousportions of the aggregated input data to compile the identity data, forexample. The operations may also include transmitting, by a transceiverof the communication interface, an indication of the identity data tothe computing device possibly taking the form of one or more of thewearable computing devices described above.

In some embodiments, the machine- or computer-readable instructions maycause the server device to perform additional operations such asauthenticating, by the one or more processing components, the useraccount based on the identity data. For example, consider FIG. 5, wherean exemplary system 500 includes a wearable computing device 502 thatmay, for example, take the form of a smartphone or the computing device100. Further, the system 500 includes merchant devices 504 and 506 thatmay, for example, be located in stores 520 and 522, respectively, shownon a map 508 for illustrative purposes. As shown, the multiple stores518, 520, 522, and 524 are located proximate to one another.

In addition to active input data such as fingerprint data and voicecommand data, the identity data may include passive input data receivedby the sensors of the wearable computing device 502. For example,consider a scenario where the identity data includes movement data basedon the way a user moves while wearing the computing device 502 proximateto the store 520, possibly while shopping for clothing. The identitydata may include other forms of data related to the way the user talks,walks, stops walking, and/or changes direction proximate to the store520, among other factors to recognize the user while shopping and/orlooking at items in the store 520. Based on the identity data used torecognize the particular user, the user account may be authenticated.Further, the operations may include enabling the wearable computingdevice 502 to access the merchant device 504 at the store 520, themerchant device 506 at the store 522, and/or an application (e.g., anonline shopping website) based on the authentication, possibly topurchase an item at the stores 520 and/or 522.

In some embodiments, the authentication of the user account may be usedto securely authenticate activities of the user account. For example,enabling the user account to access the merchant devices 504, 506,and/or the applications may include securing the input data and theidentity data from the merchant devices 504, 506, and/or theapplications. As such, the merchant devices 504, 506, and/or theapplications may be unable to access the input data and the identitydata. The merchant devices 504, 506, and/or the applications may beblocked from accessing the input data and the identity data, leavingsuch data secure from third parties.

In some embodiments, aggregating the input data as described above mayinclude determining shopping pattern data from the input data. Forexample, considering the scenario above where the wearable computingdevice 502 is proximate to the store 520. The server device maydetermine data (e.g., movement data and/or position data) indicative ofthe user shopping proximate to the stores 518-524. Thus, the machine- orcomputer-readable instructions described above may further cause theserver device to perform additional operations such as determining, bythe one or more processing components, a recommended item based on theshopping pattern data. For example, the server device may determine aclothing item at the store 522 that the user may be interested in basedon the way the user slows down and/or pauses to view clothes at thestore 520. In some instances, the stores 520 and 522 may have one ormore similar styles of clothes and/or possibly similar sales or deals.Thus, the operations may include determining an indication of therecommended item at the store 522 and transmitting the indication ofrecommended item to the wearable computing device 502.

In some embodiments, aggregating the input data may include determiningsize data associated with the user account from the input data. Forexample, the wearable computing device 502 may be worn on the user'swrist as described above in relation to FIG. 1B. As such, the aggregatedinput data may include size data indicative of the user's head, possiblybased on the wearable computing device 502 measuring the circumferenceof the user's head. Thus, the machine- or computer-readable instructionsdescribed above may further cause the server device to performadditional operations such as determining, by the one or more processingcomponents, a recommended item (e.g., a hat) at a store location 522based on the size data. Thus, the operations may include determining anindication of the recommended item at the store location 522 andtransmitting the indication of the recommended item and the storelocation 522 to the wearable computing device 502. In some instances,transmitting the indication of the recommended item to the wearablecomputing device 502 may authenticate one or more purchases ofrecommended items via the wearable computing device 502 under the useraccount.

FIG. 6 is a flowchart of an exemplary method 600 for aggregating inputdata and determining identity data, according to an embodiment. Notethat one or more steps, processes, and/or methods described herein maybe omitted, performed in a different sequence, and/or combined forvarious types of applications.

At step 602, the method 600 may include aggregating, by one or moreprocessing components of a server device, input data associated with anumber of inputs received by a computing device. The one or moreprocessors of the server device may aggregate the input data in anymanner described above in relation to FIGS. 1-5. For example, the one ormore processors may aggregate input data received by a smartphone, awearable computing device, and/or an attachable computing device.

At step 604, the method 600 may include determining, by the one or moreprocessing components of the server device, identity data of a useraccount based on the aggregation of the input data, where the identitydata indicates one or more activities of the user account. The one ormore processors of the server device may determine the identity data ofthe user account in any manner described above in relation to FIGS. 1-5.For example, the one or more processors may determine identity data ofthe user account based on the aggregation of input data includingmovement data received by the smartphone, wearable computing device,and/or the attachable computing device.

At step 606, the method 600 may include transmitting, by a communicationinterface of the server device, an indication of the identity data to acomputing device configured to access the user account. As noted, thecomputing device may be the wearable computing device, the attachablecomputing device, and/or any other types of devices described above suchas a smart phone.

In some embodiments, the method 600 may further include authenticatingthe user account based on the identity data. For example, consider FIG.7, where an exemplary system 700 includes a computing device 702 thatmay, for example, take the form of a smartphone or the computing device100. Further, the system 700 includes an attachable computing device 703that may, for example, take the form of the computing device 200. Assuch, the method 600 may include authenticating the user account basedon the identity data. For example, the identity data may be determinedbased on the input data received by the wearable computing device 702and the attachable computing device 702, where the input data mayindicate that the wearable computing device 702 and the attachablecomputing device 703 are linked as described above in relation to FIGS.1-2. Linking the wearable computing device 702 with the attachablecomputing device 703 may indicate that the user has possession of boththe wearable computing device 702 and the attachable computing device703, thereby authenticating the user account. Thus, the method 600 mayfurther include enabling the user account to access one or moreapplications based on the authentication, possibly to make one or morepurchases.

In some embodiments, enabling the user account to access the one or moreapplications includes securing the identity data from the one or moreapplications such that the one or more applications are unable to accessthe identity data. As shown in FIG. 7, for example, the user accountassociated with the wearable computing device 702 may access one or moreapplications on the merchant device 704 to make a purchase. Yet, the oneor more applications may be unable to access data, such as the identitydata, from the wearable computing device 702. As shown, the system 700may include merchant devices 704 and 706 that may, for example, belocated in stores 720 and 722, respectively, shown on a map 708 providedfor illustrative purposes. As shown, the multiple stores 718, 720, 722,and 724 are located proximate to one another.

In some embodiments, aggregating the input data includes determiningshopping pattern data from the input data. For example, consider thescenario above where the wearable computing device 702 and theattachable computing device 703 are linked and located proximate to thestore 720. The one or more processing components may determine inputdata (e.g., movement data and/or positioning data) from the devices 702and 703 indicative of the user walking proximate to the stores 720-724.For example, input data from the wearable computing device 702 may becompared with the input data from the attachable device 703, and thecompared data may be determined as the shopping pattern data. Thus, themethod 600 may further include determining, by the one or moreprocessing components, a recommended item based on at least the shoppingpattern data. For example, the processing components may determine anitem at store 722 that the user is likely to be interested in based onthe data received by the devices 702 and 703, indicating the user isviewing clothes at the store 720. In this scenario, the stores 720 and722 may include similar types of clothes, garments, apparels, and/oraccessories. Thus, the method 600 may further include transmitting anindication of the recommended item to the wearable computing device 702.

In some embodiments, aggregating the input data may include determiningsize data associated with the user account from the input data. Forexample, the wearable computing device 702 and the attachable computingdevice 703 may receive input data associated with size data (e.g., thelength of the user's pants), possibly where the wearable computingdevice 702 is worn on the user's head and the attachable computingdevice 703 is attached to the user's belt buckle or a similar accessoryon the user's waist. In particular, the wearable computing device 703may approximate a first distance from the user's head to the groundusing its sensors and distance approximation. By subtracting a seconddistance (e.g., between the wearable computing device 702 and theattachable computing device 703) from the first distance, the length ofthe user's pants may be estimated. As such the method 600 may furtherinclude determining, by the one or more processing components, arecommended item (i.e., a pair of pants) at a store location 722 basedon the size data. Further, the method 600 may include transmitting anindication of the recommended item at the store location to the wearablecomputing device 702.

In some embodiments, the method 600 may include causing the computingdevice to display at least one of the identity data and one or morerecommended items. For example, consider FIG. 8, where a computingdevice 800 displays identity data and a recommended item. The computingdevice 800 may take the form of a smartphone or the computing device100. For example, the wearable computing device 800 may include the lens802, the side component 806, the middle component 810, and the display812 that may take the form of the lens 102, the side component 106, themiddle component 110, and the display 112, respectively, of thecomputing device 100. As shown, the wearable computing device 800 mayreceive identity data 804 from the server device, causing the wearablecomputing device 800 to display the recommended item 808 at the storelocation 822. As shown, the identity data 804 may include an indication,“You are here,” and the store location 822 on a map 828 such that theuser can navigate to the store location 822. Further, the display 812may be transparent where the identity data 804 and the store location822 on the map 828 may be partially see-through. As such, the display812 may provide an augmented reality such that the user can see theidentity data 804, the recommended data 808, and the map 828 whilelooking at a field-of-view (FOV) through the lens 802. Notably, thestores 818, 820, 822, and 824 correspond to the stores 718, 720, 722,and 724, respectively, as described above.

The present disclosure, the accompanying figures, and the claims are notintended to limit the present disclosure to the precise forms orparticular fields of use disclosed. As such, it is contemplated thatvarious alternate embodiments and/or modifications to the presentdisclosure, whether explicitly described or implied herein, are possiblein light of the disclosure. Having thus described embodiments of thepresent disclosure, persons of ordinary skill in the art will recognizethat changes may be made in form and detail without departing from thescope of the present disclosure.

What is claimed is:
 1. A system comprising: a non-transitory memory; andone or more hardware processors coupled to the non-transitory memory andconfigured to read instructions from the non-transitory memory to causethe system to perform operations comprising: receiving, from one or moresensors associated with a wearable device of a first user, firstmovement data indicating that the wearable device has been removed froma first part of a body of the first user, wherein a user account of thefirst user is associated first movement data corresponding to a movementpattern of the first part of the body of the first user while the firstuser was previously engaged in a first activity and while the wearabledevice was not separated from the first user; receiving, from the one ormore sensors, second movement data indicating that the wearable devicehas been removed from the first part of the body of the first user;after the receiving the second movement data, receiving, from the one ormore sensors, third movement data corresponding to a movement pattern ofthe first part of a body of a second user currently wearing the wearabledevice while the second user is detected engaging in the first activity;detecting that the second user is at a predefined location; analyzingthe third movement data at least in part by comparing a pattern of thethird movement data with a pattern of the first movement data, whereinthe comparing further comprises comparing the first movement data of thefirst user when the first user is at the predefined location with thethird movement data of the second user when the second user is at thepredefined location; determining, based at least in part on theanalyzing of the third movement data, that the second user is differentfrom the first user; and denying an authentication of the second user inresponse to the determining that the second user is different from thefirst user.
 2. The system of claim 1, wherein the user account isfurther associated with first size data of the at least the first partof the body of the first user, wherein the operations further comprisereceiving, from the one or more sensors, second size data of the firstpart of the body of the second user, and wherein the determining isfurther based on comparing the first size data with the second sizedata.
 3. The system of claim 1, wherein the third movement data isreceived continually from the one or more sensors throughout anengagement of the first activity by the second user.
 4. The system ofclaim 1, wherein the operations further comprise securing the firstmovement data and the third movement data from one or more third partyapplications.
 5. The system of claim 1, wherein the user account isfurther associated with first biometric data of the first user, whereinthe operations further comprise receiving, from the one or more sensors,second biometric data of the second user, the first biometric data andthe second biometric data comprising at least one of Deoxyribonucleicacid (DNA) data, salivary data, sweat data, pulse data, hair data, naildata, or blood data, and wherein the determining is further based oncomparing the first biometric data with the second biometric data. 6.The system of claim 1, wherein the one or more sensors includes anaccelerometer, a gyroscope, a compass, a barometer, a capacitive sensor,a haptic sensor, a temperature sensor, an ambient light sensor, a soundsensor, an image sensor, a biometric sensor, a moisture sensor, anelectrode, or a chemical sampling sensor.
 7. The system of claim 1,wherein the first movement data comprises a movement of a hand, a wrist,or a head of the first user, or a stride pattern of the first user, andwherein the third movement data comprises a movement of a hand, a wrist,or a head of the second user, or a stride pattern of the second user. 8.The system of claim 1, wherein the determining comprises determiningthat the second user is a thief.
 9. A method comprising: receiving, fromone or more sensors associated with a wearable device of a first user,first movement data indicating that the wearable device has been removedfrom a first part of a body of the first user, wherein a user account ofthe first user is associated first movement data corresponding to amovement pattern of the first part of the body of the first user whilethe first user was previously engaged in a first activity and while thewearable device was not separated from the first user; receiving, fromthe one or more sensors, second movement data indicating that thewearable device has been removed from the first part of the body of thefirst user; after the receiving the second movement data, receiving,from the one or more sensors, third movement data corresponding to amovement pattern of the first part of a body of a second user currentlywearing the wearable device while the second user is detected engagingin the first activity; detecting that the second user is at a predefinedlocation; analyzing the third movement data at least in part bycomparing a pattern of the third movement data with a pattern of thefirst movement data, wherein the comparing further comprises comparingthe first movement data of the first user when the first user is at thepredefined location with the third movement data of the second user whenthe second user is at the predefined location; determining, based atleast in part on the analyzing of the third movement data, that thesecond user is different from the first user; and denying anauthentication of the second user in response to the determining thatthe second user is different from the first user.
 10. The method ofclaim 9, wherein the third movement data is received continually fromthe one or more sensors throughout an engagement of the first activityby the second user.
 11. The method of claim 9, further comprisingsecuring the first movement data and the third movement data.
 12. Themethod of claim 9, wherein the one or more sensor includes anaccelerometer, a gyroscope, a compass, a barometer, a capacitive sensor,a haptic sensor, a temperature sensor, an ambient light sensor, a soundsensor, an image sensor, a biometric sensor, a moisture sensor, anelectrode, or a chemical sampling sensor.
 13. The method of claim 9,wherein the first movement data comprises a movement of a hand, a wrist,or a head of the first user, or a stride pattern of the first user, andwherein the third movement data comprises a movement of a hand, a wrist,or a head of the second user, or a stride pattern of the second user.14. The method of claim 9, wherein the user account is furtherassociated with first size data of the at least the first part of thebody of the first user, wherein the method further comprises receiving,from the one or more sensors, second size data of the first part of thebody of the second user, and wherein the determining is further based oncomparing the first size data with the second size data.
 15. The methodof claim 9, wherein the determining comprises determining that thesecond user is a thief.
 16. A non-transitory computer-readable mediumhaving stored thereon executable instructions that causes a system toperform operations comprising: receiving, from one or more sensorsassociated with a wearable device of a first user, first movement dataindicating that the wearable device has been removed from a first partof a body of the first user, wherein a user account of the first user isassociated first movement data corresponding to a movement pattern ofthe first part of the body of the first user while the first user waspreviously engaged in a first activity and while the wearable device wasnot separated from the first user; receiving, from the one or moresensors, second movement data indicating that the wearable device hasbeen removed from the first part of the body of the first user; afterthe receiving the second movement data, receiving, from the one or moresensors, third movement data corresponding to a movement pattern of thefirst part of a body of a second user currently wearing the wearabledevice while the second user is detected engaging in the first activity;detecting that the second user is at a predefined location; analyzingthe third movement data at least in part by comparing a pattern of thethird movement data with a pattern of the first movement data, whereinthe comparing further comprises comparing the first movement data of thefirst user when the first user is at the predefined location with thethird movement data of the second user when the second user is at thepredefined location; determining, based at least in part on theanalyzing of the third movement data, that the second user is differentfrom the first user; and denying an authentication of the second user inresponse to the determining that the second user is different from thefirst user.
 17. The non-transitory computer-readable medium of claim 16,wherein the user account is further associated with first size data ofthe at least the first part of the body of the first user, wherein theoperations further comprise receiving, from the one or more sensors,second size data of the first part of the body of the second user, andwherein the determining is further based on comparing the first sizedata with the second size data.
 18. The non-transitory computer-readablemedium of claim 16, wherein the first movement data comprises a movementof a hand, a wrist, or a head of the first user, or a stride pattern ofthe first user, and wherein the third movement data comprises a movementof a hand, a wrist, or a head of the second user, or a stride pattern ofthe second user.
 19. The non-transitory computer-readable medium ofclaim 16, wherein the one or more sensors includes an accelerometer, agyroscope, a compass, a barometer, a capacitive sensor, a haptic sensor,a temperature sensor, an ambient light sensor, a sound sensor, an imagesensor, a biometric sensor, a moisture sensor, an electrode, or achemical sampling sensor.
 20. The non-transitory computer-readablemedium of claim 16, wherein the determining comprises determining thatthe second user is a thief.